Data communication system and method for communicating data in a vehicle

ABSTRACT

A system includes an energy management system configured to be communicatively coupled with a communication system of a vehicle that travels on a trip along a route. The energy management system is configured to be removably coupled with the communication system such that the energy management system is mechanically disengageable from the communication system. The energy management system is further configured to receive data parameters from the communication system and to generate at least one of a trip plan or a control message for the vehicle based on the data parameters. The trip plan and/or the control message dictates tractive and braking efforts of the vehicle during the trip. The energy management system is configured to communicate the trip plan and/or the control message to the communication system for the communication system to implement for controlling movement of the vehicle during the trip.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.14/101,673 (the “'673 application”), filed Dec. 10, 2013. The '673application is a continuation of U.S. application Ser. No. 13/311,306(the “'306 application”), filed Dec. 5, 2011, now U.S. Pat. No.8,620,552. The '306 application claims the benefit of U.S. ProvisionalApplication Ser. No. 61/496,353 (the “'353 application”), filed Jun. 13,2011. The entire disclosures of these applications (the '673application, the '306 application, and the '353 application) areincorporated by reference herein.

BACKGROUND

Certain vehicles (e.g., powered vehicles or vehicle consists) includecommunication systems that periodically obtain measurements related tothe health, operations, or control of the vehicle. For example,locomotives in a rail vehicle consist (“consist” referring to a group ofvehicles linked to travel together along a route, including possiblecoordinated control by one or more wired and/or wireless connections)may include communication systems that periodically receive measurementsrelated to operations of the locomotive, such as speed, horsepower,temperature, brake pressure measurements, and the like. Thesemeasurements represent data parameters of the vehicle, and the values ofthe data parameters may periodically change. For example, measurementsof speed of a traction motor may be a first data parameter, measurementsof brake pressures may be a second data parameter, and so on.

The values of the data parameters may be requested and used bycomputerized services or applications running on the vehicle and/orrunning off-board the vehicle. These services or applications performvarious functions based on the data parameters. For example, theservices or applications may control tractive operations and/or brakingoperations of the vehicle, monitor performance of the vehicle over time,record events of the vehicle, and the like. The systems that acquire thedata parameters and that are native to the vehicle, such as the systemsthat are initially installed in the vehicle, may use a communicationprotocol to form and communicate data messages that include the valuesof the data parameters. Other services or applications may use adifferent communication protocol that uses a different format tocommunicate and/or use the data messages that include the dataparameters.

The different protocols used to communicate with the various systems,services, and applications can require different communicationconfigurations to be used. For example, in order for a single device tocommunicate with systems, services, and/or applications using differentcommunication protocols, the single device may need to have differentcommunication configurations stored thereon. The communicationconfigurations can dictate the rules and criteria used for communicatingwith the systems, services, and/or applications according to thedifferent protocols.

In some known vehicles, in order to allow for communication between adevice and the systems, services, and/or applications that use differentprotocols to communicate, the various communication configurations mustbe previously stored on-board the device and the device must be manuallyconfigured to communicate with the systems, services, and/orapplications. If one or more systems, services, or applications arechanged or swapped out, the configuration of the device may need to bemanually re-configured to allow for communication between the device anda new system, service, or application that uses a different protocol.

A need exists for a system and method that allows for different systems,services, applications, and the like in a vehicle and using differentcommunication protocols to communicate with a device without requiringthe manual re-configuration of the device each time a system, service,application, and the like, using a different communication protocol, isadded to the vehicle.

BRIEF DESCRIPTION

In one embodiment, a system includes an energy management system thathas one or more processors. The energy management system is configuredto be communicatively coupled with a communication system of a vehiclethat travels on a trip along a route. The energy management system isconfigured to receive data parameters related to at least one of thevehicle, the route, or the trip from the communication system. Theenergy management system is further configured to generate at least oneof a trip plan or a control message for the vehicle based on thereceived data parameters. The at least one of the trip plan or thecontrol message dictates tractive and braking efforts of the vehicleduring the trip. The energy management system is configured tocommunicate the at least one of the trip plan or the control message tothe communication system for the communication system to implement theat least one of the trip plan or the control message to control movementof the vehicle during the trip. The energy management system isconfigured to be removably coupled with the communication system suchthat the energy management system is mechanically disengageable from thecommunication system.

In another embodiment, a system includes an interface gateway device andan energy management system. The interface gateway device is on acommunication system of a vehicle that travels on a trip along a route.The interface gateway device is configured to be communicatively coupledto a data acquisition module. The energy management system includes oneor more processors. The energy management system is configured to becommunicatively coupled to the interface gateway device. The energymanagement system is configured to be removably coupled with theinterface gateway device such that the energy management system ismechanically disengageable from the interface gateway device. Theinterface gateway device is configured to receive data parametersrelated to at least one of the vehicle, the route, or the trip from thedata acquisition module and to communicate the data parameters to theenergy management system. The energy management system is configured togenerate at least one of a trip plan or a control message for thevehicle based on the received data parameters and to communicate the atleast one of the trip plan or the control message to the interfacegateway device for the communication system to implement to control thevehicle during the trip.

In another embodiment, a method for controlling a vehicle during a tripalong a route includes determining whether a communicative coupling to acommunication system on the vehicle is established. If the communicativecoupling to the communication system is established, the method includesidentifying the communication system. The method also includesretrieving a communication configuration associated with thecommunication system that is identified. The method further includesreceiving data parameters from the communication system. The dataparameters are communicated according to the communicationconfiguration. The method includes generating at least one of a tripplan or a control message that dictates at least one of tractive effortsor braking efforts of the vehicle during the trip. The at least one ofthe trip plan or the control message is generated based on the receiveddata parameters and the capability configuration. The method alsoincludes communicating the at least one of the trip plan or the controlmessage to the communication system for the communication system toimplement the at least one of the trip plan or the control message tocontrol movement of the vehicle during the trip. The at least one of thetrip plan or the control message is communicated according to thecommunication configuration.

In another embodiment, a data communication system for a vehicleincludes an interface gateway device that is configured to becommunicatively coupled with a data acquisition module and a clientmodule. The interface gateway device is further configured to receive avalue of a data parameter related to operation of the vehicle from thedata acquisition module and to communicate the value to the clientmodule for performing a function for the vehicle. The interface gatewaydevice also is configured to determine when either of the dataacquisition module or the client module is communicatively coupled withthe interface gateway device and to implement respective communicationconfigurations associated with the data acquisition module or the clientmodule to receive the value of the data parameter from the dataacquisition module or communicate the value of the data parameter to theclient module.

In another embodiment, a data communication system for a vehicle isprovided. The system includes an interface gateway device that isconfigured to be communicatively coupled with a data acquisition moduleand with a client module. The interface gateway device is furtherconfigured to receive a value of a data parameter related to operationof the vehicle from the data acquisition module and to communicate thevalue to the client module for performing a function for the vehicle.The interface gateway device also is configured, upon systeminitialization of the interface gateway device, to cycle through aplurality of communication protocols available to the interface gatewaydevice, at each of a plurality of communication links of the interfacegateway device, until the interface gateway device has determined thatthe data acquisition module and the client module are communicativelycoupled with the interface gateway device and has identified first andsecond communication protocols of the plurality of communicationprotocols that enable the interface gateway device to communicate withthe data acquisition module and the client module, respectively.

In another embodiment, a method for communicating data in a vehicle isprovided. The method includes monitoring one or more input/output portsfor a communication link with a device, determining an identity of thedevice that is communicatively coupled with the one or more input/outputports by the communication link, selecting a communication configurationassociated with the device based on the identity of the device, andusing the communication configuration to communicate with the device.

In another embodiment, a computer readable storage medium for a vehiclehaving a processor is provided. The computer readable storage mediumincludes one or more sets of instructions that direct the processor tomonitor one or more input/output ports for a communication link with adevice, determine an identity of the device that is communicativelycoupled with the one or more input/output ports by the communicationlink, select a communication configuration associated with the devicebased on the identity of the device, and communicate with the deviceaccording to the communication configuration.

In another embodiment, a data communication system for a vehicle isprovided. The system includes a data acquisition module, a clientmodule, and an interface gateway module. The data acquisition module isconfigured to obtain a value of a data parameter related to operation ofthe vehicle. The client module is configured to use the value of thedata parameter to perform a function for the vehicle. The interfacegateway device is configured to be communicatively coupled with at leastone of the data acquisition module or the client module by one or morecommunication links. The interface gateway device is further configuredto communicate the value from the data acquisition module to the clientmodule. The interface gateway device also is configured to determinewhen the at least one of the data acquisition module or the clientmodule is communicatively coupled with the interface gateway device andto implement a communication configuration associated with the at leastone of the data acquisition module or the client module to communicatethe value of the data parameter to the at least one of the dataacquisition module or the client module.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of one embodiment of a vehicle datacommunication system disposed on-board a powered vehicle.

FIG. 2 is a schematic diagram of an interface gateway device shown inFIG. 1 in accordance with one embodiment.

FIG. 3 is another schematic illustration of the interface gateway deviceshown in FIG. 1 in accordance with one embodiment.

FIG. 4 is a flowchart of one embodiment of a method for communicatingdata in a vehicle.

FIG. 5 is a schematic diagram of one embodiment of the vehicle datacommunication system including an energy management system.

FIG. 6 is a flowchart of one embodiment of a method for controlling avehicle during a trip along a route.

DETAILED DESCRIPTION

The foregoing brief description, as well as the following detaileddescription of certain embodiments of the inventive subject matter, willbe better understood when read in conjunction with the appendeddrawings. To the extent that the figures illustrate diagrams of thefunctional blocks of various embodiments, the functional blocks are notnecessarily indicative of the division between hardware circuitry. Thus,for example, one or more of the functional blocks (for example,processors or memories) may be implemented in a single piece of hardware(for example, a general purpose signal processor, microcontroller,random access memory, hard disk, and the like). Similarly, the programsmay be stand alone programs, may be incorporated as subroutines in anoperating system, may be functions in an installed software package, andthe like. The various embodiments are not limited to the arrangementsand instrumentality shown in the drawings.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralof said elements or steps, unless such exclusion is explicitly stated.Furthermore, references to “one embodiment” of the present inventivesubject matter are not intended to be interpreted as excluding theexistence of additional embodiments that also incorporate the recitedfeatures. Moreover, unless explicitly stated to the contrary,embodiments “comprising” or “having” an element or a plurality ofelements having a particular property may include additional suchelements not having that property.

FIG. 1 is a schematic diagram of one embodiment of a vehicle datacommunication system 100 disposed on-board a powered vehicle 102. In theillustrated embodiment, the vehicle 102 is illustrated as a railvehicle, such as a locomotive. Alternatively, the vehicle 102 may beanother type of rail vehicle (such as a non-powered cargo car) or anon-rail vehicle, such as a different type of off-highway vehicle (OHV)or other vehicle. The system 100 is shown in FIG. 1 as being disposedentirely on-board the single vehicle 102. Alternatively, the system 100may be distributed among several interconnected vehicles, such as bybeing partially disposed on each of several vehicles that include thevehicle 102 and that are mechanically coupled in a consist or othergroup.

The system 100 manages the acquisition and distribution of data relatedto operations of the vehicle 102 among devices disposed on-board and/oroff-board the vehicle 102. The vehicle 102 includes one or morecomponents 104 and/or subsystems 106 that perform various operations ofthe vehicle 102. While only one component 104 and one subsystem 106 areshown in the illustrated embodiment, the system 100 may include agreater number or none of one or more of the component 104 and/orsubsystem 106. By way of example, the components 104 and/or subsystems106 of the vehicle 102 may represent a propulsion subsystem thatgenerates tractive effort for the vehicle 102 to propel itself (e.g., asubsystem that includes one or more traction motors), a brakingsubsystem that generates braking effort for the vehicle 102 to slow downor stop itself from moving, a wireless communication system that is usedto communicate with another vehicle or system outside of the vehicle 102(e.g., a radio transceiver with antenna), a sensor that obtains datarelated to the vehicle 102 (e.g., a brake air pressure sensor, a fuelgauge, a cargo sensor, a global positioning system (GPS) receiver, orthe like), a user interface device that receives input from an operatorof the vehicle 102 to control the vehicle 102, and the like. Theprevious list provides a non-limiting example of the types of components104 and/or subsystems 106 that may be used. In one embodiment, anydevice, sensor, system, subsystem, memory, module, assembly, processor,or the like may be used as the component 104 and/or subsystem 106. Oneor more of the components 104 and/or subsystems 106 may be disposedoff-board the vehicle 102, such as by being disposed on-board anothervehicle that is mechanically coupled or interconnected with the vehicle102 (e.g., a mechanically linked other vehicle in a rail vehicleconsist).

The component 104 and subsystem 106 are operably coupled with controllerdevices 108 (e.g., “Controller #1” and “Controller #2”). As used herein,the term “operably coupled” includes two or more controllers, devices,sensors, systems, subsystems, assemblies, processors, memories, modules,or the like that are connected by one or more wired and/or wirelesscommunication links, such as cables, busses, other conductive pathways(e.g., copper wires), wireless networks, fiber optic cables, and thelike, such as to enable communication of data therebetween. Thecontroller devices 108 are generally referred to by the reference number108 and individually referred to by the reference numbers 108 a and 108b. While two controller devices 108 are shown, alternatively, a smalleror larger number of controller devices 108 may be provided.

The controller devices 108 interface with the components 104 and/orsubsystems 106 to obtain values of one or more data parameters from thecomponents 104 and/or subsystems 106. The controller devices 108 mayinclude one or more electronic devices that obtain values of one or moreof the data parameters from the components 104 and/or subsystems 106. Inone embodiment, one or more of the controller devices 108 may directoperations of the components 104 and/or subsystems 106. The controllerdevices 108 can include sensors that obtain one or more of the dataparameters from the components 104 and/or subsystems 106, processors orother logic-based devices, along with associated circuitry, that monitorand/or control the components 104 and/or subsystems 106, and the like.

The data parameters obtained by the controller devices 108 representdata values related to operations of the vehicle 102. As used herein,the term “operations” can refer to performance of the vehicle 102 (e.g.,related to actions and events performed in propelling goods and/orpassengers), control of the vehicle 102 (e.g., throttle and/or brakesettings), and/or health conditions of the vehicle 102 (e.g., a statusof the vehicle 102 such as whether maintenance is required for thevehicle 102 or one or more components 104 and/or subsystems 106 aremalfunctioning).

For example, if the subsystem 106 includes a propulsion subsystem thatincludes one or more traction motors and/or a sensor operably coupledwith the propulsion subsystem, the controller device 108 b may obtainmeasurements of horsepower generated by the traction motors,measurements of wheel slippage of the wheels connected to the tractionmotors, temperatures measurements of bearings, wheels, and/or axlesinterconnected with the traction motors, and the like. If the subsystem106 includes a braking subsystem that includes air brakes and/orregenerative brakes, the controller device 108 b may obtain measurementsof air pressure in the air brakes and/or reservoirs connected to the airbrakes, measurements of current obtained from the regenerative brakes,settings of the air brakes and/or regenerative brakes, and the like. Ifthe component 104 includes an antenna that is used to communicate withanother vehicle or system outside of the vehicle 102, then thecontroller device 108 a can obtain data parameters representative ofwhich communication channels are being used, quality of service (QoS)measurements of communication over the antenna, and the like. If thecomponent 104 includes a sensor, then the controller device 108 a canobtain data parameters representative of quantities measured or sensedby the sensor. The above provides a non-exclusive set of data parametersthat can be obtained by the controller devices 108. One or more othertypes of data parameters that relate to operations of the vehicle 102may be obtained.

The controller devices 108 are operably coupled with data acquisitionmodules 110 (e.g., “Source #1” and “Source #2”). As used herein, theterm “module” includes a hardware and/or software system that operatesto perform one or more functions. For example, a module may include acomputer processor, controller, or other logic-based device thatperforms operations based on instructions stored on a tangible andnon-transitory computer readable storage medium, such as a computermemory. Alternatively, a module may include a hard-wired device thatperforms operations based on hard-wired logic of the device. The modulesshown in the attached figures may represent the hardware that operatesbased on software or hardwired instructions, the software that directshardware to perform the operations, or a combination thereof.

The data acquisition modules 110 are generally referred to by thereference number 110 and individually referred to by the referencenumbers 110 a, 110 b, and 110 c. While two data acquisition modules 110are shown, alternatively, a smaller or larger number of data acquisitionmodules 110 may be provided. The data acquisition modules 110 interfacewith the controller devices 108 to acquire the values of the dataparameters obtained by the controller devices 108 from the components104 and/or subsystems 106. While each of the data acquisition modules110 is shown as only interfacing or communicating with a singlecontroller device 108, alternatively, one or more of the dataacquisition modules 110 may interface with a plurality of the controllerdevices 108.

In the system 100, the data acquisition modules 110 may be referred toas “sources” of the available data parameters as the data acquisitionmodules 110 acquire the data parameters from the controller devices 108and produce the data parameters for consumption (e.g., use) by one ormore other parts of the system 100, such as client modules 114 describedbelow.

The data acquisition modules 110 are operably coupled with an interfacegateway device 112 (“Interface Gateway”) in the illustrated embodiment.The interface gateway device 112 manages and controls the distributionof the data parameters through the system 100, as described in moredetail below. For example, the interface gateway device 112 may act asan information gateway between a back end portion 116 of the system 100and a front end portion 118 of the system 100. The back end portion 116of the system 100 can generate the data that is used by the front endportion 118 of the system 100 to perform one or more functions, asdescribed below. For example, the back end portion 116 can obtain valuesof the data parameters that are communicated via the interface gatewaydevice 112 to the client modules 114, which use the values to performvarious functions.

The back end portion 116 acquires the values of the data parameters asdata and conveys the data in electronic messages (e.g., signals) to theinterface gateway device 112. The interface gateway device 112 canreceive the data via the messages and communicate the data to the clientmodules 114.

The client modules 114 (“Client #1” “Client #2,” and “Client #3”) areoperably coupled with the interface gateway device 112. The clientmodules 114 are generally referred to by the reference number 114 andindividually referred to by the reference numbers 114 a, 114 b, 114 c.While three client modules 114 are shown, alternatively, a smaller orlarger number of client modules 114 may be provided. The client modules114 perform functions based on, or by using, at least some of the dataparameters. For example, the client modules 114 interface with theinterface gateway device 112 to receive the values of the dataparameters from the interface gateway device 112. The client modules 114send requests for data parameters to the interface gateway device 112and may wait for a response from the interface gateway device 112 thatincludes the values of the data parameters. The client modules 114 mayinclude or alternatively may be referred to as subscriber modules, whichare “listening” devices that obtains the values of the data parametersused by the module by joining an address or a group, such as by issuinga “join” request to the interface gateway device 112 that joins themodule to a multicast IP address. The interface gateway device 112 mayperiodically multicast the values of the data parameters to the IPaddress and the modules that subscribe to the IP address can receive thevalues. As described above, the client modules 114 may receive the datarepresentative of the values of the data parameters in a format that isdifferent from the format used by the back end portion 116 due to theinterface gateway device 112 converting the format of the data.

A variety of functions related to operations of the vehicle 102 may beperformed by the client modules 114. By way of example, a client module114 may provide a digital video recorder (e.g., a locomotive digitalvideo recorder or LDVR provided by General Electric Company) thatobtains video recordings based on the data parameters (e.g., the dataparameters may indicate when and/or where to record video). As anotherexample, a client module 114 may provide asset tracking services (e.g.,asset tracking system or ATS provided by General Electric Company) thatmonitors locations of assets (e.g., non-powered units and/or cargo suchas goods and/or passengers) being propelled or conveyed by the vehicle102 based on the data parameters.

A client module 114 may provide control services that control operationsof the vehicle 102 and/or one or more other vehicles coupled orinterconnected with the vehicle 102. For example, a client module 114may use the data parameters to control the tractive efforts (e.g., bycontrolling throttle settings) provided by a propulsion subsystem of thevehicle 102 and/or to control braking efforts (e.g., by controllingbrake settings) provided by brakes of the vehicle 102. The client module114 may be part of a positive train control (PTC) system or adistributed power (DP) system that controls the tractive efforts and/orbraking efforts of the vehicle 102 and/or one or more other poweredunits and/or non-powered units of a consist based on the dataparameters. Alternatively, one or more of the client modules 114 mayprovide an energy management application that controls tractive effortand/or braking effort of the vehicle 102 (and/or one or more otherpowered units or vehicles of a consist) based on the data parameters.For example, a client module 114 may control throttle settings and/orbrake settings based on a variety of factors represented by the dataparameters, such as the types (e.g., horsepower provided) of poweredunits in a consist, the weight of cargo carried by the consist, thegrade and/or curvature of a track that the vehicle 102 travels along, ageographic location obtained by a GPS receiver, and the like, in orderto reduce fuel consumption by the consist. One example of such an energymanagement application may be the Trip Optimizer™ system provided byGeneral Electric Company.

Other examples of a function provided by the client modules 114 caninclude control of cab signaling of a rail vehicle, an event recorderthat monitors and records events related to operation of the vehicle102, a location recorder that determines a geographic location of thevehicle 102 based on GPS sensor data received by a GPS receiver as adata parameter, fuel monitoring, radio monitoring, a visual display ofoperations or conditions of one or more components 104 and/or subsystems106 of the vehicle 102, and the like. The above examples are providedfor illustration and are not intended to be limiting on all embodimentsof the presently described subject matter.

In one embodiment, the interface gateway device 112 may use differentcommunication configurations for communicating with different components104, subsystems 106, and/or client modules 114. A communicationconfiguration may specify the parameters and settings used tocommunicate data messages between two devices, such as between theinterface gateway device 112 and one or more of the data acquisitionmodules 110 and/or client modules 114. For example, a communicationconfiguration may specify a communication protocol to be used tocommunicate the data messages between the devices. A “communicationprotocol” includes a set of one or more formats and/or rules forexchanging messages between the devices. Different communicationprotocols may use different types of signaling mechanisms,authentication techniques, error detection mechanisms, messagecorrection techniques, and the like. A communication protocol may definethe format, semantics, and/or synchronization of messages betweendevices using the protocol. A format of a communication protocol canrepresent the syntax in which data is recorded, read, and/orcommunicated between the devices in messages. For example, the format ofa communication protocol may be based on a syntax of the protocol, suchas one or more rules that define how various combinations of symbols,alphanumeric text, binary bits (e.g., 0's and l's), and the like, arecombined and used to represent and communicate data between atransmitter and a recipient that are communicating using the protocol.

A communication configuration may specify a sequence of how messages areexchanged between devices. For example, a first communicationconfiguration may involve a message “handshake” between the devices inorder to communicate between the devices. A message handshake caninclude two-sided messaging, such as a first device sending a firstmessage to a second device and the second device sending a secondmessage, such as a response or confirmation of receipt of the firstmessage, to the first device. A different, second communicationconfiguration may not require a message handshake, and instead maypermit or provide for one-sided messaging. One-sided messaging caninclude a first device sending a first message to a second devicewithout a second message being sent back to the first device from thesecond device.

In one embodiment, a communication configuration can include a list orset of one or more data parameters that are to be communicated orpublished to a device. For example, one or more client modules 114 maybe associated with a communication configuration that specifies apredetermined list or set of data parameters. The values of the dataparameters in the list or set can be published or transmitted to theclient modules 114 that use the communication configuration via theinterface gateway device 112. Different communication configurations caninclude different lists or sets of data parameters that are to bepublished.

A communication configuration can include a list or set of one or moredata parameters that are available for communication or publication to adevice. For example, not all data parameters that are obtained by thecontroller devices 108 may be available to all client modules 114 due toreasons of incompatibility, security, and the like. The communicationconfiguration for a client module 114 may specify a subset of the dataparameters that are obtained by the controller devices 108. For example,if the controller devices 108 obtain a set of one hundred dataparameters, the communication configuration for a client module 114 mayonly include a subset of ten of the data parameters. The set of dataparameters that are obtained by the controller devices 108 may bereferred to as the “available data parameters.” The communicationconfiguration can limit the publication or communication of dataparameters to the client module 114 to the subset of the available dataparameters defined by the communication configuration.

In one embodiment, a communication configuration may specify whether alog or record is to be kept of the activities of the interface gatewaydevice 112 and/or the device communicating with the interface gatewaydevice 112. For example, the communication configuration may listactivities, such as the data parameters, communication errors, requestsfor data parameters, and the like, that are transmitted by a dataacquisition module 110 or client module 114 to the interface gatewaydevice 112 and/or transmitted from the interface gateway device 112 to adata acquisition module 110 or client module 114.

The communication configurations associated with different dataacquisition modules 110, client modules 114, or other components ordevices of the system 100 may be stored as configuration files on acomputer readable storage medium, such as a hard disc, flash drive, RAM,ROM, CD, DVD, or other type of memory, that is accessible by theinterface gateway device 112. As described below, the interface gatewaydevice 112 can monitor which data acquisition modules 110, clientmodules 114, or other components or devices of the system 100 arecommunicatively coupled with the interface gateway device 112. By“communicatively coupled,” it is meant that two devices, systems,subsystems, assemblies, modules, components, and the like, are joined byone or more wired or wireless communication links, such as by one ormore conductive (e.g., copper) wires, cables, or buses; wirelessnetworks; fiber optic cables, and the like. When the interface gatewaydevice 112 determines that a data acquisition module 110, client module114, or other component or device is so coupled with the interfacegateway device 112, the interface gateway device 112 may automaticallyload the corresponding communication configuration into the interfacegateway device 112. By “load,” it is meant that the interface gatewaydevice 112 obtains the communication settings of the communicationconfiguration and uses the settings to communicate with the dataacquisition module 110, client module 114, or other component or device.

FIG. 2 is a schematic diagram of the interface gateway device 112 inaccordance with one embodiment. The interface gateway device 112 mayinclude a hardware and/or software system that operates to perform oneor more functions. In the illustrated embodiment, the interface gatewaydevice 112 includes a processor 200 and a computer readable storagemedium, or a memory 202, that perform various functions describedherein. Alternatively, the interface gateway device 112 may includeseveral modules that operate to cause the processor 200 to performvarious functions described herein. For example, the interface gatewaydevice 112 can be programmed or installed onto the memory 202 or intothe processor 200 instead of including the processor 200 and/or memory202. The processor 200 can include a microprocessor, controller, orequivalent control circuitry. The memory 202 can include a tangible andnon-transitory computer readable storage medium, such as a physicaldevice that stores data on a temporary or permanent basis for use by theprocessor 200. The memory 202 may include one or more volatile and/ornon-volatile memory devices, such as random access memory (RAM), staticrandom access memory (SRAM), dynamic RAM (DRAM), another type of RAM,read only memory (ROM), flash memory, magnetic storage devices (e.g.,hard discs, floppy discs, or magnetic tapes), optical discs, and thelike.

The modules of the interface gateway device 112 include a monitoringmodule 210. The monitoring module 210 monitors one or more input/outputports of the interface gateway device 112 to determine when a device,such as a data acquisition module 110 or a client module 114, iscommunicatively coupled with the interface gateway device 112. Forexample, the data acquisition modules 110 and/or the client modules 114may include electrical connectors 204, 206, 208 that mate withinput/output ports 300, 302, 304 (shown in FIG. 3) of the interfacegateway device 112 to communicatively couple the data acquisitionmodules 110 and the client modules 114 with the interface gateway device112.

With continued reference to FIG. 2, FIG. 3 is another schematicillustration of the interface gateway device 112 in accordance with oneembodiment. The illustration of FIG. 3 may show a portion of an exteriorhousing 306 of the interface gateway device 112. The interface gatewaydevice 112 includes the input/output ports 300, 302, 304 disposed on thehousing 306. The ports 300, 302, 304 represent electrical connectors,such as electrical receptacles or plugs, that physically mate (e.g.,receive or are inserted into) with the connectors 204, 206, 208 of thedata acquisition modules 110 and the client modules 114 to communicateelectronic messages therebetween.

In the illustrated embodiment, the ports 300 include Ethernet jacks 300a, 300 b that are shaped to receive an Ethernet plug. For example, theports 300 may receive one or more of the connectors 204, 206, 208 thatis an Ethernet plug, such as an 8P8C plug, a 6P6C plug, a 6P4C plug, a4P4C plug, and the like. Alternatively, one or more of the ports 300 mayinclude an Ethernet plug and one or more of the connectors 204, 206, 208may include an Ethernet jack. In another embodiment, connectors otherthan Ethernet jacks and plugs are used for the ports 300 and one or moreof the connectors 204, 206, 208.

The ports 302 include serial receptacles 302 a, 302 b that are shaped toreceive a serial connector plug in the illustrated embodiment. Forexample, the ports 302 may receive one or more of the connectors 204,206, 208 that is serial plug, such as an RS 232 plug, an RS 422 plug, orthe like. The ports 302 include conductive receptacles 308 that receiveconductive pin of the serial plugs to conductively couple the ports 302with one or more of the connectors 204, 206, 208. Alternatively, one ormore of the ports 302 may include a serial plug and one or more of theconnectors 204, 206, 208 may include a serial receptacle. In anotherembodiment, connectors other than serial receptacles and plugs are usedfor the ports 302 and one or more of the connectors 204, 206, 208. Theports 304 include serial plugs 304 a, 304 b, 304 c, 304 d that areshaped to be received in a serial receptacle. For example, the ports 304may include an RS 232 plug, an RS 422 plug, or the like, havingconductive pins 310 that are received in conductive receptacles (such asthe conductive receptacles 308) in one or more of the connectors 204,206, 208.

The number and/or type of input/output ports 300, 302, 304 shown in FIG.3 are provided as examples. A greater or smaller number of theinput/output ports 300, 302, and/or 304 may be provided. Additionally,one or more input/output ports other than the input/output ports 300,302, and/or 304 may be included in the interface gateway device 112.

As shown in FIG. 2, in one embodiment, one or more of the input/outputports of the interface gateway device 112 that is used to communicatewith one or more of the data acquisition modules 110 and/or the clientmodules 114 is a wireless communication channel. For example, instead ofphysically mating a connector with one or more of the input/output ports300, 302, 304, one or more of the data acquisition modules 110 (such asthe data acquisition module 110 b) and/or the client modules 114 (suchas the client module 114 c) may communicate with the interface gatewaydevice 112 through a wireless communication channel. A wirelesscommunication channel may include one or more frequencies or range offrequencies over which the interface gateway device 112 may wirelesslycommunicate with the data acquisition device 110 and/or the clientmodule 114. The interface gateway device 112 includes an antenna 212that wirelessly communicates (e.g., transmits and/or receives) messagesover one or more wireless communication channels with the dataacquisition module 110 and/or the client module 114.

Returning to the discussion of the interface gateway device 112 shown inFIG. 2, the monitoring module 210 monitors one or more of theinput/output ports of the interface gateway device 112 to determine whena device, such as a data acquisition module 110 or a client module 114,is communicatively coupled with the interface gateway device 112. Withrespect to the physical input/output ports 300, 302, 304 (e.g., theports that include plugs inserted into receptacles, receptacles thatreceive plugs, fiber optic cables that are disposed close to or touchingeach other, or other connectors that mate with each other), themonitoring module 210 may determine when a conductive connection is madebetween conductors of a connector of a data acquisition module 110 orclient module 114 and a connector of the interface gateway device 112.For example, the monitoring module 210 may determine when a conductivepin of a connector 204, 206, 208 is received in a conductive receptacleof an input/output port 300, 302, 304 in the interface gateway device112, or when a conductive receptacle of the connector 204, 206, 208receives a conductive pin of an input/output port 300, 302, 304. In oneembodiment, the monitoring module 210 determines when a module iscoupled with one or more input/output ports of the interface gatewaydevice 112 by determining when an electric circuit is closed by themating of a connector 204, 206, 208 and an input/output port 300, 302,304.

With respect to wireless communication links, the monitoring module 210can monitor one or more wireless communication channels to determinewhen a data acquisition module 110 and/or a client module 114 iscommunicatively coupled with the interface gateway device 112. Forexample, the monitoring module 210 may scan through a plurality offrequencies or wireless communication channels over the antenna 212 todetermine which, if any, of the communication channels are being used tocommunicate data with the interface gateway device 112.

An identification module 214 determines which device is communicativelycoupled with the interface gateway device 112. For example, once themonitoring module 210 determines that a data acquisition module 110and/or a client module 114 is physically coupled or wirelessly coupledwith an input/output port (physical port or wireless port/communicationchannel) of the interface gateway device 112, the identification module214 may identify a type of data acquisition module 110 or client module114 that is coupled with the interface gateway device 112. A “type” ofdata acquisition module 110 or client module 114 can include a categoryor group of data acquisition modules 110 or client modules 114 that usethe same communication configurations described above. In oneembodiment, a type of data acquisition module 110 or client module 114can include a category or group of data acquisition modules 110 orclient modules 114 that acquire one or more of the same data,communicate one or more of the same messages or use the same messageformats, request one or more of the same data parameters, provide one ormore of the same functions for the vehicle 102 (shown in FIG. 1),monitor one or more of the same operations of the vehicle 102, and thelike.

In one embodiment, the identification module 214 may identify which dataacquisition module 110 or client module 114 is communicatively coupledwith an input/output port of the interface gateway device 112 byexamining data communicated from the data acquisition module 110 orclient module 114 to the interface gateway device 112 through theinput/output port. For example, the data acquisition module 110 orclient module 114 may transmit one or more messages that includeidentifying information to the interface gateway device 112 through theinput/output port. The messages can include identifying information suchas an address (e.g., IP address) or an alphanumeric bitstring that isunique to the data acquisition module 110, the client module 114, or agroup or type of data acquisition modules 110 or client modules 114. Forexample, the messages communicated from the data acquisition module 110or client module 114 may include header frames having identifyinginformation of the module 110, 114 that transmitted the message.

In another embodiment, the input/output port 300, 302, 304 to which thedata acquisition module 110 or client module 114 is mated and/or theconnector 204, 206, 208 of the data acquisition module 110 or clientmodule 114 may include keying features that permit a subset of the dataacquisition modules 110 or client modules 114 to use the port 300, 302,304. For example, and as shown in FIG. 3, the different ports 300, 302,304 may have different shapes such that a subset of the connectors 204,206, 208 are shaped to mate with the ports 300, 302, 304. The subset ofthe connectors 204, 206, 208 that can mate with the ports 300, 302, 304may have complimentary shapes to the ports 300, 302, 304 while otherconnectors 204, 206, 208 do not have complimentary shapes. Thecomplimentary shaped connectors 204, 206, 208 and ports 300, 302, 304can mate with each other while non-complimentary shaped connectors 204,206, 208 and ports 300, 302, 304 may not be able to mate with eachother. In one embodiment, the keying features can include one or moreprotrusions, slots, receptacles, or other features that compliment eachother such that some connectors 204, 206, 208 and ports 300, 302, 304are able to mate with each other while other connectors 204, 206, 208and ports 300, 302, 304 are unable to mate with each other. Theidentification module 214 can determine which data acquisition module110 or client module 114 is mated which the port 300, 302, 304 when thedata acquisition module 110 or client module 114 mates with the port300, 302, 304. For example, if the keying features only permit one typeof the data acquisition module 110 or client module 114 to mate with aparticular port 300, 302, 304, then the identification module 214 canidentify the data acquisition module 110 or client module 114 when thedata acquisition module 110 or client module 114 mates with the port300, 302, 304.

A configuration module 216 of the interface gateway device 112determines the communication configurations for the data acquisitionmodules 110 and/or the client modules 114 that are communicativelycoupled with the interface gateway device 112. In one embodiment, oncethe monitoring module 210 determines that the data acquisition module110 or client module 114 is coupled with the interface gateway device112 and the identification module 214 identifies which data acquisitionmodule 110 or client module 114 is coupled with the interface gatewaydevice 112, the configuration module 216 obtains the configurationsettings for the corresponding data acquisition modules 110 and/orclient modules 114. For example, the configuration module 216 mayretrieve the settings for the communication configuration associatedwith the data acquisition modules 110 and client modules 114 from thememory 202.

As described above, the communication configuration associated with adata acquisition module 110 or client module 114 may specify the rulesand/or procedures for communicating messages between the dataacquisition module 110 or client module 114 and the interface gatewaydevice 112. The configuration module 216 may load the communicationconfigurations for the data acquisition module 110 or client module 114by conveying the communication configuration settings to a communicationmodule 218 described below.

An update module 220 can obtain the communication configurations fordata acquisition modules 110 and/or client modules 114 that are notstored on the memory 202. For example, if the communicationconfiguration for the data acquisition module 110 or client module 114is not stored on the memory 202, the update module 220 may acquire thecommunication configuration for the data acquisition module 110 orclient module 114. The update module 220 can acquire the communicationconfiguration by querying an off-board device (e.g., a computer having awireless transmitter or antenna) for the communication configuration.The off-board device may transmit the communication configuration to theupdate module 220 via the antenna 212. Alternatively, an on-board device(e.g., a computer device or other memory disposed on the vehicle 102shown in FIG. 1) may provide the communication configuration to theupdate module 220. The update module 220 may store the communicationconfiguration on the memory 202 and/or convey the communicationconfiguration to the configuration module 216.

The communication module 218 receives the communication configurationfrom the memory 202, the configuration module 216, or the update module216 and uses the communication configuration to control thecommunication of messages to and/or from the interface gateway device112 with the data acquisition modules 110 and/or client modules 114 thatare communicatively coupled with the interface gateway device 112. Asdescribed above, the communication configurations can specify theparameters and settings used by the communication module 218 tocommunicate data messages with the data acquisition modules 110 and/orclient modules 114. The communication module 218 may concurrently usedifferent communication configurations with different data acquisitionmodules 110 and/or client modules 114.

In another embodiment, upon application start (or commencement ofoperation of interface gateway device 112 (or similar device) starts allof its internal applications which correspond to every system and orsubsystem with which the interface gateway device 112 is capable ofcommunicating. For example, the interface gateway device 112 may begininternal algorithms, software applications, and the like, that permit orcontrol communication between the interface gateway device 112 and everysource 110 and/or client 114 with which the interface gateway device 112is configured or is capable of communicating. The interface gatewaydevice 112 attempts to establish communications via a handshakingprocess or other similar method using the input/output port 300, 302,304. The interface gateway device 112 monitors the input/output port300, 302, 304 in an order to determine if the correct response isreceived from the source 110 and/or client 114 connected to theinput/output port 300, 302, 304. For example, during the handshakingprocess, the interface gateway device 112 may transmit one or moresignals to a source 110 or client 114 through a correspondinginput/output port 300, 302, 304. The source 110 or client 114 may theneither respond with a designated confirmation response (e.g., confirmingthe handshake connection between the interface gateway device 112 andthe source 110 or client 114), respond with a response that differs fromthe confirmation response (e.g., notifying that the handshake connectionis not confirmed or established), or may not provide any response.

If the correct response (e.g., the designated confirmation response) isreceived from the source 110 or client 114, the interface gateway device112 declares that communications with the source 110 or client 114 areestablished. The interface gateway device 112 adds that source 110 orclient 114 to a list of connected devices that is maintained by theinterface gateway device 112. If no response or an incorrect response isreceived (e.g., the confirmation response is not received or a differentresponse is received), then the interface gateway device 112 may try toestablish communication with another source 110 or client 114 on thesame input/output port 300, 302, 304. The interface gateway device 112may sequentially cycle through a list of sources 110 and/or clients 114that may be connected to the input/output port 300, 302, 304 until thedesignated confirmation response is received or all sources 110 and/orclients 114 in the list have been attempted without receiving thedesignated confirmation response. Alternatively, the interface gatewaydevice 112 may move on to the next input/output port 300, 302, 304 andrepeat the process described above. Once the interface gateway device112 establishes a list of all the connected sources 110 and/or clients114 (or other devices), the interface gateway device 112 applies theappropriate internal configuration files. This permits the interfacegateway device 112 to provide the functionality defined for that systemand or subsystem.

FIG. 4 is a flowchart of one embodiment of a method 400 forcommunicating data in a vehicle. The method 400 may be used inconjunction with one or more embodiments of the system 100 (shown inFIG. 1) described above. For example, the method 400 may be used with asystem in a vehicle that acquires values of data parameters and sends orpublishes the values of the data parameters to one or more clientmodules to permit the client modules to perform one or more functionsrelated to the vehicle.

At 402, one or more input/output ports are monitored to determine if acommunication link is established. For example, the input/output ports300, 302, 304 (shown in FIG. 3) and/or one or more wirelesscommunication channels may be monitored to determine when a dataacquisition module 110 (shown in FIG. 1) and/or a client module 114(shown in FIG. 1) is physically mated to one or more of the ports 300,302, 304 and/or is communicatively coupled with the interface gatewaydevice 112 (shown in FIG. 1) via a wireless communication channel.

At 404, a determination is made as to whether a communication link isdetected. For example, a determination may be made as to whether aconnector 204, 206, 208 (shown in FIG. 2) of a data acquisition module110 (shown in FIG. 1) and/or a client module 114 (shown in FIG. 1) ismated with an input/output port 300, 302, 304 (shown in FIG. 3) of theinterface gateway device 112 (shown in FIG. 1). As another example, adetermination may be made as to whether a data acquisition module 110and/or a client module 114 is wirelessly transmitting data to theinterface gateway device 112 via one or more communication channels. Ifa communication link is detected, flow of the method 400 may continue to406. On the other hand, if no communication link is detected, flow ofthe method 400 may return to 402.

At 406, an identity of the device that is communicatively coupled viathe communication link is determined. For example, the interface gatewaydevice 112 (shown in FIG. 1) may determine which of the acquisition datamodules 110 (shown in FIG. 1) and/or client modules 114 (shown inFIG. 1) is communicatively coupled with the interface gateway device112. The identity of the acquisition data module 110 and/or clientmodule 114 may be the identity of a group or type of acquisition datamodules 110 and/or client modules 114, as described above.

At 408, a determination is made as to whether the communicationconfiguration for the communicatively coupled device is available. Forexample, the interface gateway device 112 (shown in FIG. 1) maydetermine if a communication configuration file associated with theidentified data acquisition module 110 (shown in FIG. 1) and/or clientmodule 114 (shown in FIG. 1) is stored on the memory 202 (shown in FIG.2) disposed on-board the vehicle 102 (shown in FIG. 1). If thecommunication configuration for the identified device is not available,then the communication configuration may need to be acquired in order toconfigure the communications with the identified device. As a result,flow of the method 400 may continue to 410. On the other hand, if thecommunication configuration for the identified device is available, thenflow of the method 400 may proceed to 412.

At 410, the communication configuration for the identified device isobtained. For example, the interface gateway device 112 (shown inFIG. 1) may wirelessly download the communication configuration from acomputer device disposed off-board the vehicle 102 (shown in FIG. 1) viathe antenna 212 (shown in FIG. 2). Alternatively, the interface gatewaydevice 112 may download the communication configuration from a computerdevice disposed on-board the vehicle 102.

At 412, the communication configuration for the identified device isimplemented. For example, the settings, protocols, formats, and thelike, that are used to communicate data messages with the identifieddevice are used by the interface gateway device 112 (shown in FIG. 1) tocommunicate with the identified device. The interface gateway device 112may use different communication configurations for different dataacquisition modules 110 (shown in FIG. 1) and/or client modules 114(shown in FIG. 1).

In one embodiment, a plurality of different communication configurationsis stored in a common location, such as on the memory 202 (shown in FIG.2). The interface gateway device 112 (shown in FIG. 1) may select andimplement (e.g., put into use for communication) the communicationconfiguration applicable to the identified data acquisition module 110(shown in FIG. 1) or client module 114 (shown in FIG. 1).

FIG. 5 is a schematic diagram of one embodiment of the vehicle datacommunication system 100 and an energy management system 502. Thevehicle data communication system 100 shown in FIG. 5 includes at leastsome of the same components or parts shown in FIG. 1. For example, theinterface gateway device 112 in FIG. 5 is communicatively coupled to aback end portion 116 of the vehicle data communication system 100, whichincludes one or more data acquisition modules 110 (e.g., “Source(s)”),one or more controllers 108, and one or more components 104 and/orsubsystems 106. In the illustrated embodiment, the subsystems 106include the propulsion subsystem 504 and the braking subsystem 506, andthe components 104 include the GPS receiver 508 and the user interfacedevice 510, each of which is described above with reference to FIG. 1.The subsystems 504, 506 and the components 508, 510 illustrated in FIG.5 may represent only a subset of the total number of subsystems 106and/or components 104 in the vehicle data communication system 100.

In an embodiment, the energy management system 502 is separate from thevehicle data communication system 100, but is configured to communicatewith the system 100. For example, the energy management system 502 maybe separate from, but communicatively coupled to, the communicationsystem 100 via a conductive connection or a wireless connection. In analternative embodiment, the energy management system 502 is part of thesystem 100 and represents one of the client modules 114 that define thefront end portion 118 of the system 100. For example, the energymanagement system 502 may be one of the client modules 114 thatcommunicates in the system 100 when the energy management system 502 iscommunicatively coupled to the interface gateway device 112, or anotherdevice in the system 100.

The energy management system 502 is configured to perform functionsbased on, or by using, at least some of the data parameters acquired bythe data acquisition modules 110 on the back end portion 116 of thesystem 100. At least one of the functions of the energy managementsystem 502 may be to provide control services that control operations ofthe vehicle 102 (shown in FIG. 1) and/or one or more other vehiclescoupled to or interconnected with the vehicle 102 based on the receiveddata parameters. The energy management system 502 may use the dataparameters to control the tractive efforts (e.g., by controllingthrottle settings) provided by the propulsion subsystem 504 of thevehicle 102 and/or to control braking efforts (e.g., by controllingbrake settings) provided by braking subsystem 506 of the vehicle 102.The energy management system 502 may control throttle and brake settingsby generating control messages or signals that are transmitted to therespective propulsion and braking subsystems 504, 506, or to thecontrollers 108 that control the subsystems 504, 506. Optionally, theenergy management system 502 may generate control messages forcontrolling other subsystems 106, components 104, and/or client modules114 on the vehicle, such as a user interface device 510, lights,speakers and/or horns, and the like. Some control messages or signalsmay be transmitted to components and/or subsystems on other vehiclesinterconnected to the vehicle 102 within the same consist, in a positivetrain control (PTC) system, or in a distributed power (DP) system. Thecontrol messages may be based on information related to the vehicle 102,the vehicle consist, and/or a trip of the vehicle 102.

The energy management system 502 provides control services that controloperations of the vehicle 102 (shown in FIG. 1) and/or a vehicle consistthat includes the vehicle based on a variety of factors represented bythe data parameters in order achieve one or more designated goals duringa trip of the vehicle 102 while meeting or adhering to set constraints.One typical goal of the energy management system 502 is to reduce theamount of fuel or other energy source consumed during the trip. Otherdesignated goals that may be taken into account by the energy managementsystem 502 include reducing travel time, reducing wear on the vehicle102 and other interconnected vehicles, reaching a destination at apredefined time, increasing throughput of vehicle systems on a vehiclenetwork, reducing emissions, reducing noise, and the like. The setconstraints may include speed limits, other regulatory restrictions(such as noise, emissions, etc.), and the like. One example of theenergy management system 502 is the Trip Optimizer™ system provided byGeneral Electric Company.

The energy management system 502 may not be an integral component of thevehicle 102 and/or the vehicle data communication system 100. In anembodiment, the energy management system 502 is removable relative tothe vehicle data communication system 100 and/or the vehicle 102. Forexample, the energy management system 502 is mechanically disengageablefrom the communication system 100 and/or the vehicle 102. When theenergy management system 502 is mechanically disengaged from thecommunication system 100, the energy management system 502 is notcommunicatively coupled to the communication system 100 such that nocommunications are successfully transmitted between the systems 100,502. Thus, to establish a communicative coupling between the systems100, 502, the energy management system 502 may need to be mechanicallyengaged to the interface gateway device 112 or another device in thecommunication system 100, such that an electrical conductive path (e.g.,via electrical contacts, circuits, conductive wires, and the like) or anelectrical inductive path (e.g., via inductors, coils, transformers, andthe like) is formed to provide a communication link between the systems100, 502. When the energy management system 502 is mechanically engagedwith the communication system 100, the systems 502, 100 arecommunicatively coupled and may communicate messages therebetween viaconductive and/or inductive paths. In one or more embodiments, theenergy management system 502 may be an add-on device or application thatis connected to or installed in the vehicle 102 after the vehicle 102 isassembled, offered for sale, or sold. The energy management system 502may be removable from the vehicle 102, such as by disconnecting thedevice or deleting the application.

In FIG. 5, the energy management system 502 is a removable, discretedevice that includes a housing 512 and a cable 514 extending from thehousing 512. The cable 514 is used to communicatively couple the energymanagement system 502 to the system 100 (e.g., to the interface gatewaydevice 112 in the illustrated embodiment). The cable 514 provides aconductive current path between the interface gateway device 112 and thehousing 512 to electrically connect the interface gateway device 112 andthe energy management system 502. An electrical connector 516, such as aplug or a receptacle, at a distal end of the cable 514 is configured tomechanically mate to an input/output port 518 disposed on the exteriorhousing 306 of the interface gateway device 112. The port 518 representsan electrical connector that complements the electrical connector 516 onthe cable 514. The port 518 may be one of the ports 300, 302, 304 shownin FIG. 3. The electrical connector 516 removably couples to the port518 along a mating axis 520.

In one embodiment, the energy management system 502 may becommunicatively disconnected or uncoupled from the vehicle datacommunication system 100 when the electrical connector 516 is not matedto the port 518 or any other port or connector in the system 100. Whencommunicatively uncoupled, the energy management system 502 does notreceive any data parameters and does not perform functions for thevehicle data communication system 100, such as providing controlservices or generating trip plans, as described below.

The energy management system 502 may be portable and able to be used bya different communication system on a different vehicle, such as adifferent vehicle in the same consist as the vehicle 102 or a vehicle ina different vehicle system. The energy management system 502 isconfigured to establish a communicative connection with the vehicle datacommunication system on the different vehicle in order to receiveinformation, such as data parameters, and provide control services. Forexample, the energy management system 502 may be communicatively coupledto the vehicle data communication system 100 during one or more trips ofthe vehicle 102, and the energy management system 502 may be moved tothe different vehicle communication system for one or more subsequenttrips of the different vehicle. The different vehicle data communicationsystem may differ from the vehicle data communication system 100 withrespect to the number, types, and arrangement of the devices (forexample, interface gateway devices, data acquisition devices,controllers, components, subsystems, and/or client modules) that make upthe systems, the communication configurations used to communicate in thesystems, the functional capabilities of the systems, and the like.Although the vehicle data communication systems may vary, the energymanagement system 502 is configured to communicate with each of thecommunication systems.

In an embodiment, the energy management system 502 is configured toidentify the vehicle data communication system 100 that the energymanagement system 502 is communicatively coupled to, retrieve acommunication configuration based on the identified communication system100, and communicate with the communication system 100 according to thecommunication configuration to receive data parameters and providecontrol services for the vehicle along a trip based on the received dataparameters.

When the energy management system 502 is communicatively coupled to thevehicle data communication system 100, the energy management system 502is configured to communicate directly or indirectly with some or all ofthe various parts of the system 100, such as the interface gatewaydevice 112, the data acquisition modules 110, the controllers 108, thecomponents 104 and/or subsystems 106, and/or the client modules 114. Viasuch communications, the energy management system 502 is able to receivedata parameters and other information from various devices in the system100. The energy management system 502 is also able to send or transmitinformation, such as control signals, to various devices in the system100. In FIG. 5, the energy management system 502 is shown poised formaking a direct electrical connection to the interface gateway device112, through which the energy management system 502 communicates withthe back end portion 116 and/or the front end portion 118 of thecommunication system 100. In an alternative embodiment, the energymanagement system 502 may couple directly to another device of thecommunication system 100, such as a controller 108 (or another controlsystem on the vehicle 102), a data acquisition module 110, or a clientmodule 114, instead of coupling directly to the interface gateway device112. For example, the energy management system 502 may indirectly coupleto the interface gateway device 112 via a client module 114 in directelectrical connection with the interface gateway device 112.

The energy management system 502 shown in FIG. 5 includes a processor522 and a computer readable storage medium, or memory 524, that performvarious functions described herein. The processor 522 and the memory 524may be housed in the housing 512 when the energy management system 502is a plug-in device. The processor 522 can include a microprocessor,controller, or equivalent control circuitry. The memory 524 can includea tangible and non-transitory computer readable storage medium, such asa physical device that stores data on a temporary or permanent basis foruse by the processor 522. The memory 524 may include one or morevolatile and/or non-volatile memory devices, such as random accessmemory (RAM), static random access memory (SRAM), dynamic RAM (DRAM),another type of RAM, read only memory (ROM), flash memory, magneticstorage devices (e.g., hard discs, floppy discs, or magnetic tapes),optical discs, and the like.

In an alternative embodiment, instead of being a plug-in device, theenergy management system 502 is a software application that is readableby and/or downloadable onto the vehicle data communication system 100,such as onto the interface gateway device 112, a controller 108, oranother control system on the vehicle 102 (shown in FIG. 1). Thus,instead of including the processor 522 and the memory 524, the energymanagement system 502 may be installable, downloadable, or otherwisereadable on a processor and/or a memory of the vehicle datacommunication system 100, such as the processor 200 and/or the memory202 (both shown in FIG. 2) of the interface gateway device 112. Theenergy management system 502 may be stored as one or more files on acomputer readable storage medium that is local to (for example, disposedon) the vehicle 102. The files may be computer-implemented instructionsthat direct a processor to perform various functions. The local storagemedium may be a hard disc, flash drive, RAM, ROM, CD, DVD, or other typeof memory, such as the memory 202. The energy management system 502 maybe transmitted to the local storage medium from an external storagedevice, such as a CD, DVD, flash memory, external hard drive, a server,and the like. For example, the energy management system 502 may bedownloaded on the local storage medium (such as the memory 202) from aremote server via a network connection, such as the Internet, a localaccess network connection, or the like. The files of the energymanagement system 502 may be transmitted via a wired communication link,such as a cable, a wireless communication link, such as via a wirelessdata network, or a combination wired and wireless communication pathway.

In another alternative embodiment, the energy management system 502 is asoftware application that remains contained on the external storagedevice instead of being transferred onto a local storage device in thevehicle data communication system 100. For example, the vehicle datacommunication system 100 may be communicatively coupled to the energymanagement system 502 when the external storage device (e.g., CD, DVD,flash device, external hard drive, etc.) is electrically connected to alocal device, such as the interface gateway device 112 or another devicewith an appropriate input/output port, in the vehicle data communicationsystem 100. Yet, although the energy management system 502 communicateswith communication system 100 when the external storage device isconnected, the files of the energy management system 502 are not copiedor otherwise moved from the external storage device to the local device(e.g., the interface gateway device 112).

The energy management system 502 shown in FIG. 5 may include severalmodules that operate to cause the processor 522 to perform variousfunctions described herein. The modules of the energy management system502 include an identification module 526, a configuration module 528, acommunication module 530, a plan generating module 532, and a tripmonitoring module 534. In the alternative embodiments in which theenergy management system 502 is a software application operable on alocal device of the vehicle data communication system 100, the files ofthe energy management system 502 may direct a processor of the device(such as the processor 202 of the interface gateway device 112) toperform the same or similar functions as caused by the modules 526-534.Thus, the following description of the modules 526-534 may be applicableto both the embodiment of the energy management system 502 as theplug-in device shown in FIG. 5 and the embodiment of the energymanagement system 502 as a software application on an external storagedevice.

The identification module 526 determines information about the vehicledata communication system 100 to which the energy management system 502is connected. For example, once the energy management system 502recognizes the establishment of a communicative connection between theenergy management system 502 and the vehicle data communication system100, the identification module 526 may identify a type of the vehicledata communication system 100. The “type” of the vehicle datacommunication system 100 may include information about the various partsor devices that make up the communication system 100 and the vehicle 102on which the communication system 100 is disposed. More specifically,the information about the vehicle data communication system 100 mayinclude the number, arrangement, and kinds of the devices that make upthe communication system 100. The information also may identify thespecific manufacturer, model, and/or year of at least some of thedevices. The information about the vehicle 102 may include themanufacturer, model, and/or year of the vehicle 102.

In one embodiment, the identification module 526 may identify thevehicle data communication system 100 communicatively coupled with theenergy management system 502 by examining data communicated from theinterface gateway device 112 to the energy management system 502 throughthe cable 514. For example, the vehicle data communication system 100may transmit one or more identification messages that includeidentifying information to the energy management system 502. Theidentification messages may be transmitted to the energy managementsystem 502 from the input/output port 518 of the interface gatewaydevice 112 through the cable 514. The identification messages mayinclude an address (e.g., IP address) or an alphanumeric bit string thatis unique to the vehicle data communication system 100 (or a group ortype of vehicle data communication systems that includes thecommunication system 100). For example, the identification messagescommunicated from the interface gateway device 112 may include headerframes having identifying information specific to the vehicle datacommunication system 100 that transmits the messages.

The configuration module 528 of the energy management system 502 isconfigured to determine the communication configurations for the vehicledata communication system 100 communicatively coupled to the energymanagement system 502. The energy management system 502 uses thecommunication configurations to allow for communicating messages to andfrom the devices of the communication system 100. As described above,the communication configurations associated with the vehicle datacommunication system 100 may specify the rules and/or procedures forcommunicating messages between the energy management system 502 and thevehicle data communication system 100. The configuration module 528 mayload the communication configurations for the vehicle data communicationsystem 100 by conveying communication configuration settings to acommunication module 530, described below.

The configuration module 528 may also be configured to determinefunctional capability configurations of the vehicle data communicationsystem 100. The energy management system 502 uses the capabilityconfigurations to determine the command content of control messages sentto the communication system 100. The capability configurationsassociated with the vehicle data communication system 100 may specifythe available control settings and formats for controlling one or moreof the devices of the vehicle data communication system 100. Forexample, the capability configurations of the propulsion subsystem 504may indicate available throttle settings of integers between “1” and“8,” such that throttle setting “8” used more tractive effort thansetting “1.” When sending a control message to the propulsion subsystem504, the energy management system 502 uses the configuration by issuinga control command for a throttle setting between (or including) theintegers “1” and “8” in the content of the message, instead of, forexample, throttle settings “9” or “6.5.”

In another example, the capability configurations may indicate thecontrol settings and formats for the specific user interface 510 in thevehicle data communication system 100. Some user interfaces havedifferent capabilities than other user interfaces, such as thecapability to display images, to display video, and to produce sounds.In addition, different user interfaces have different presentationsettings and formats for presenting user output information andreceiving user input information. For example, the user interface 510may be configured with the capability to display a dynamic,time-variable display. The dynamic display may depict current and/orupcoming geographical elements, such as track elevation, for the segmentof route being traversed and/or to be traversed by the vehicle 102. Inanother example, the display may show active route restrictions and/orrules, such as speed limits, for the current and/or upcoming segment ofroute during the trip. The capability configuration settings indicatethe capability of the user interface 510 to receive and display dynamicinformation on the display and the available message formats for suchinformation to be used by the user interface 510. Alternatively, thecapability configuration may indicate that the user interface 510 onlyhas the capability to display static images.

In one embodiment, once the identification module 526 identifies whichvehicle data communication system 100 is coupled with the energymanagement system 502, the configuration module 528 obtainscommunication and/or capability configurations for the correspondingvehicle data communication system 100. The settings of the communicationand/or capability configurations may be applicable to the vehicle datacommunication system 100 as a whole, or may be specific to individualdevices or groups of devices in the vehicle data communication system100. For example, different configuration settings may be obtained forthe data acquisition modules 110 than the client modules 114 and/or theinterface gateway device 112. Different configuration settings may alsobe obtained for different devices within the same group of devices. Forexample, the configuration module 528 may obtain different configurationsettings for interfacing with a data acquisition module 110 thatcommunicates with the user interface 510 than a different dataacquisition module 110 that communicates with the propulsion subsystem504 or the braking subsystem 506.

In an embodiment, the configuration module 528 may retrieve the settingsfor the communication and/or capability configurations from the memory524 of the energy management system 502. Thus, the communication and/orcapability configurations for the vehicle data communication system 100may be stored in the memory 524. Since the energy management system 502may be configured to communicatively couple to different vehicle datacommunication systems that include different devices, the memory 524 maybe loaded with communication and/or capability configurations formultiple different vehicle data communication systems, including for thevarious different devices (e.g., data acquisition modules, components,subsystems, client modules, etc.) that make up the communicationsystems.

Optionally, if the communication and/or capability configurations forthe identified vehicle data communication system 100 (or for one or moreof the devices thereof) are not stored on the memory 524, theconfiguration module 528 may acquire the missing communication and/orcapability configurations. The configuration module 528 may query anoff-board device (e.g., a computer having a wireless transmitter orantenna) for the configurations. For example, energy management system502 may include a communication system (not shown) that has both atransmitter and a receiver, or a transceiver. The communication systemis used to wirelessly communicate with the off-board device. Theoff-board device may transmit the missing communication and/orcapability configurations to the energy management system 502, where theconfigurations are stored in the memory 524.

Alternatively, or in addition, if the communication and/or capabilityconfigurations for the identified vehicle data communication system 100are not stored on the memory 524, an on-board device may provide themissing configurations to the configuration module 528. The on-boarddevice may be a computer device or other memory disposed on the vehicle102 (shown in FIG. 1) or may be a device in the vehicle datacommunication system 100, such as the interface gateway device 112.Thus, in addition to communicating identification information, thevehicle data communication system 100 may be configured to communicateconfiguration information of the communication system 100 to the energymanagement system 502. For example, the vehicle data communicationsystem 100 may be configured to only send such configuration informationin response to a query from the energy management system 502 requestingthe configuration information that the memory 524 of the energymanagement system 502 lacks.

The communication module 530 of the energy management system 502receives the communication configuration for the vehicle datacommunication system 100 from the memory 524 or the configuration module528 and uses the communication configuration to control thecommunication of messages to and/or from the communication system 100.As described above, the communication configurations may specify theparameters and settings used by the communication module 530 to receivedata messages from the communication system 100 and to communicatecontrol messages to the communication system 100. The communicationmodule 218 may concurrently use different communication configurationswith different devices, such as different data acquisition modules 110and/or client modules 114, of the communication system 100. As describedabove, the contents of the control messages sent from the communicationmodule 530 are generated using the capability configurations of thecommunication system 100, such that control commands in the controlmessages are able to be implemented by the appropriate devices in thecommunication system 100.

Optionally, the energy management system 502 includes a plan generatingmodule 532 which used data parameters received from the vehicle datacommunication system 100 to generate a trip plan for the vehicle 102(shown in FIG. 1). The plan generating module 532 processes the receiveddata parameters to generate the trip plan. The trip plan may dictate oneor more operations of the propulsion subsystem 504 and/or the brakingsubsystem 506 during a trip of the vehicle 102 in order to meet one ormore goals, such as reducing fuel consumption, as described above. Thedictated operations may be specific to different segments of the trip.For example, in a segment in which the vehicle 102 traverses a steepincline, the dictated operations according to the trip plan may directthe propulsion subsystem 504 to increase the tractive efforts as thevehicle 102 approaches and/or enters that incline segment. The trip planmay direct the propulsion subsystem 504 to increase the suppliedtractive efforts by a larger amount if the vehicle 102 is carryingand/or propelling a significantly heavy cargo than would otherwise beincreased if the data indicated a lighter cargo load. Thus, the dictatedoperations, according to the trip plan, may be used to control thepropulsion subsystem 504 to change the tractive efforts of thepropulsion subsystem 504 as the vehicle 102 travels over differentsegments of the trip.

The plan generating module 532 receives various data parameters relatingthe vehicle 102, the vehicle data communication system 100, the trip,and the like, to generate the trip plan. Once the trip plan isgenerated, the communication module 530 may communicate the entire tripplan, or control messages based on the trip plan, to the vehicle datacommunication system 100 for implementation by the communication system100. Thus, bi-directional communications between the energy managementsystem 502 and the vehicle data communication system 100 are used toform and implement the trip plan, as the control messages sent to thevehicle data communication system 100 from the energy management system502 are based at least in part on information (e.g., data parameters)received by the energy management system 502 from the communicationsystem 100.

The plan generating module 532 uses various information to generate thetrip plan, including mission data, vehicle data, route data, and/orupdate thereto. Vehicle data includes information about the vehicle 102(shown in FIG. 1), the vehicle consist, and/or cargo being propelled bythe vehicle 102. For example, vehicle data may represent cargo content(such as information representative of cargo being transported by thevehicle 102) and/or vehicle information (such as model numbers,manufacturers, horsepower, and the like, of the vehicle 102). Missiondata includes information about a current or upcoming trip by thevehicle 102. By way of example only, mission data may include scheduleinformation (such as a departure time and an arrival time at thedestination location), station information (such as the location of abeginning station where the upcoming trip is to begin and/or thelocation of an ending station where the trip ends), restrictioninformation (such as work zone identifications, or information onlocations where the route is being repaired or is near another routebeing repaired and corresponding speed/throttle limitations on thevehicle), and/or operating mode information (such as speed/throttlelimitations on the vehicle 102 in various locations, slow orders, andthe like). Route data includes information about the route or track uponwhich the vehicle 102 travels during the trip. For example, the routedata may include information about locations of damaged sections of aroute, locations of route sections that are under repair orconstruction, the curvature and/or grade of a route, GPS coordinates ofthe route, and the like.

Optionally, at least some mission data, vehicle data, and route data fora trip is communicated to the energy management system 502 from anon-board scheduler device (not shown). The on-board scheduler device maybe a component 106, a subsystem 104, or a client module 114 of thevehicle data communication system 100. Alternatively, or in addition, atleast some of the mission data, vehicle data, and route data for a tripare received by the energy management system 502 from an operator byinputting the data into the vehicle data communication system 100 usingthe user interface 510.

The plan generating module 532 may be configured to update the trip planduring a trip based on received data parameters that differ in valuefrom the data parameters used to generate the trip plan. For example,the plan generating module 532 may generate a revised trip plan inresponse to, for example, updated route data that indicates that anupcoming segment of track is under repair or construction. The revisedtrip plan may re-route the vehicle 102 along a different segment oftrack. At least some of the data parameters received during the trip aresent from the vehicle data communication system 100, such as from thecomponents 104, the subsystems 106, and/or the client modules 114, andanalyzed by the trip monitoring module 534, described below.

In an alternative embodiment, the plan generating module 532 may selecta previously generated trip plan from a number of such trip plans storedin the memory 524 of the energy management system 502 instead ofgenerating an initial trip plan or instead of generating a revised tripplan during the trip. The plan generating module 532 may select the tripplan to retrieve from the memory 524 based on the data parametersreceived from the vehicle data communication system 100. In anotherexample, the plan generating module 532 may receive one or more tripplans from an on-board or off-board device, such as via a wirelesstransmission of data, instead of generating the trip plan or retrievingthe trip plan from the memory 524.

The trip monitoring module 534 of the energy management system 502 isconfigured to monitor the progress of the vehicle 102 (shown in FIG. 1)along the trip relative to the trip plan and generate control messagesthat are used to control the movements of the vehicle 102 such that thevehicle 102 moves according to the trip plan. For example, the tripmonitoring module 534 may monitor the progress of the vehicle 102 alongthe trip by receiving data parameters from vehicle data communicationsystem 100 in real-time as the vehicle 102 travels, and analyzing thereceived data with reference to the trip plan.

In an embodiment, the trip monitoring module 534 may receive dataparameters from various devices in the vehicle data communication system100, including the propulsion subsystem 504, the braking subsystem 506,the GPS receiver 508, the user interface 510, and other components 104and/or subsystems 106. For example, the propulsion and the brakingsubsystems 504, 506 may communicate current tractive and brakingsettings, respectively, as well as current power usage, and powergenerated (e.g. during generative braking). The GPS receiver 508 sendscurrent location information of the vehicle 102 to the energy managementsystem 502 for tracking the location of the vehicle 102. Sensors, suchas speedometers, accelerometers, fuel level sensors, brake pressuresensors, and the like, deliver respective data parameters (e.g., currentspeed, acceleration, remaining fuel amount, pressure of brake lines,etc.) to the energy management system 502. The user interface 510 maytransmit operator input information to the energy management system 502,such as commands to increase or decrease tractive efforts, allowing theenergy management system 502 to track the operator's actions to controlthe vehicle 102. Other examples of data parameters that may betransmitted to the trip monitoring module 534 include time, temperature,weather conditions, wear measurements, or the like.

The trip monitoring module 534 analyzes the received data parameters andcompares the information to the trip plan to determine the content andrecipients of control messages to generate for controlling the vehicle102 according to the trip plan. For example, if the analysis revealsthat the vehicle 102 is running at a speed slower than the trip planinstructs, then the trip monitoring module 534 determines to send acontrol message to the propulsion subsystem 504 to increase tractiveefforts and/or to the braking subsystem 506 to decrease braking efforts,in order to increase the speed of the vehicle 102. Optionally, thecontent of the control messages may be used to control other functionsof the vehicle 102 instead of the movement of the vehicle 102. Thecontent may include control data for the purposes of sending signals toother subsystems 106, components 104, and/or client modules 114. Forexample, the control message may alert an operator of the vehicle 102 ofa condition or fault by actuating an audible or visual alert/alarm. Thecontrol message may also be used to control devices on an exterior ofthe vehicle 102, such as a horn and/or lights. For example, as the tripmonitoring module 534 of the energy management system 502 recognizesthat the vehicle 102 is approaching a crossing, the energy managementsystem 502 may generate a control message that is used to control thehorn and lights to signal a warning to cars and other passersby that thevehicle 102 is approaching.

In one embodiment, the control messages from the trip monitoring module534 are communicated directly to the propulsion subsystem 504 and/or thebraking subsystem 506 to autonomously control the tractive efforts andbraking efforts of the vehicle 102 during the trip according to the tripplan. The control messages may be transmitted in the communicationconfigurations of the respective subsystems 504, 506 (or the controllers108 that control the subsystems 504, 506). The content of the controlmessages may include control commands generated based on the capabilityconfigurations of the respective subsystems 504, 506. For example, asthe vehicle 102 approaches a downhill segment of the route, the tripmonitoring module 534 recognizes the approaching downhill segment andconsults the trip plan, which may call for a reduction in tractionefforts and an increase in braking efforts. The trip monitoring module534 constructs or generates a control message to each of the propulsionand braking subsystems 504, 506 (or to the one or more controllers 108thereof) that includes control commands, such as increase braking effortto notch setting 5, according to the proper capability configurations ofthe subsystems 504, 506. The control message may be communicated by thecommunication module 530 according to the appropriate communicationconfiguration that allows the control message to be received by theintended recipient, such as the braking subsystem 506 or the controller108 thereof.

In an alternative embodiment, the control messages from the tripmonitoring module 534 are directed, at least initially, to the userinterface device 510 in the vehicle 102 (shown in FIG. 1) forpresentation to the operator of the vehicle 102, instead of directly tothe components 104 or subsystems 106 that implement the control commandscontained in the messages. Continuing the hypothetical example above,the trip monitoring module 534 may generate a control message to theuser interface 510 to notify the operator that the braking effort shouldbe increased along the upcoming downhill segment of the route (for thevehicle 102 to continue moving according to the trip plan). Theoperator, in response to receiving the notification, manually controlsthe braking subsystem 506 and/or the propulsion subsystem 504 to slowthe vehicle 102 as suggested by the energy management system 502. Sincethe control message is communicated to the user interface 510 instead ofdirectly to the propulsion and/or braking subsystems 504, 506, thecontent of the control message is formatted and presented according tothe capability configurations of the user interface 510. For example, ifthe user interface 510 has the capability to display a dynamic map thatshows a representation of the vehicle 102 relative to the changinggeography and/or topography along the route, then the content of thecontrol message may include graphical data to display on the userinterface 510 as the dynamic map, showing the upcoming downhill segmentof the route. If the user interface 510 has sound capability, then thecontrol message may include audio data that is used by the userinterface 510 to audibly alert the operator to upcoming changes in thetractive settings or braking settings due to the downhill segment. Thecontrol message to the user interface 510 is communicated by thecommunication module 530 using the communication configuration of theuser interface 510.

As described above, the energy management system 502 in FIG. 5 isconfigured to generate a trip plan (for example, by the plan generatingmodule 532) and to generate control messages to control the vehicle 102along the trip according to the trip plan (for example, by the tripmonitoring module 534). In other embodiments, however, an energymanagement system may be configured to generate a trip plan or togenerate control messages, but not both. For example, an energymanagement system may generate the trip plan, then communicate the tripplan to an on-board control system in the vehicle data communicationsystem 100 for the control system to implement by generating controlmessages. The control system may include or be a part of the interfacegateway device 112, the controllers 108, or the like. In anotherexample, an energy management system may not generate the trip plan, butmay monitor the progress of the vehicle 102 during a trip and generatecontrol messages to control the vehicle 102 during the trip according toa trip plan that was generated elsewhere.

FIG. 6 is a flowchart of one embodiment of a method 600 for controllinga vehicle during a trip along a route. Optionally, the method 600 may beimplemented by an energy management system, such as the energymanagement system 502 shown in FIG. 5. At 602, a determination is madewhether or not a communicative coupling exists or is established with avehicle data communication system. The vehicle data communication systemmay be, or may be similar to, the vehicle data communication system 100shown in FIG. 1. The determination may be made based on whether or notcommunications are received from a vehicle data communication system,requesting the establishment of a communicative coupling. Optionally,the determination may be made upon establishing an electrical connectionbetween an electrical connector of an energy management system and amating electrical connector of the vehicle data communication system.For example, the energy management system may be a plug-in device, asdescribed above with reference to FIG. 5. If no communicative couplingis established, flow of the method 600 returns to 602. For example,after a designated period of time, another determination of whether ofcommunicative coupling is established may be made. If a communicativecoupling is established, flow of the method 600 proceeds to 604.

At 604, the vehicle data communication system is identified. Theidentification may be a general identification of the entire systemand/or a specific identification of the number, types, and/orarrangements of devices and/or components that make up the vehicle datacommunication system. At 606, a communication configuration associatedwith the identified vehicle data communication system is retrieved. Thecommunication configuration may be retrieved from a memory of an energymanagement system. The communication configuration may designate a rulesand/or procedures for communicating messages with the vehicle datacommunication system. For example, the vehicle data communication systemincludes one or more controllers that control operations of a propulsionsubsystem and a braking subsystem of the vehicle. The communicationconfiguration is used by the one or more controllers such that when atrip plan and/or control message according to the communicationconfiguration is received by the controllers, the controllers are ableto implement the tractive settings and braking settings contained in thetrip plan and/or the control message using the respective propulsion andbraking subsystems. At 608, a capability configuration associated withthe identified vehicle data communication system is retrieved. Thecapability configuration may be retrieved from a memory of the energymanagement system or may be communicated to the energy management systemfrom the vehicle data communication system or an off-board source. Thecapability configuration indicates available control settings andformats for the vehicle data communication system or the devicesthereof.

At 610, data parameters are received from the vehicle data communicationsystem. The data parameters are communicated according to thecommunication configuration associated with the vehicle datacommunication system. The data parameters may be received prior toand/or during the trip of the vehicle. The data parameters may includedata collected by sensors, propulsion and braking subsystems, a GPSreceiver, a user interface, a trip scheduler, and the like. At 612, atrip plan and/or a control message is generated based on the receiveddata parameters. The trip plan and/or the control message dictatetractive and braking efforts of the vehicle during the trip, such asrelative to a time or location of the vehicle along the route, in orderto reduce fuel consumption, emissions, duration of trip, or attain otherspecified goals. For example, the trip plan may be generated prior tothe vehicle starting to travel on the trip based on data parametersreceived prior to the trip. The control message may be generated duringthe vehicle traveling on the trip by comparing data parameters receivedduring the trip to the trip plan that is generated prior to the trip.The trip plan and/or control message may also be generated according tothe capability configuration of the vehicle data communication system inaddition to the received data parameters. specify at least one ofavailable control settings or formats of the vehicle data communicationsystem; use the at least one capability configuration for generating acommand in the control message that is able to be implemented by thevehicle data communication system

At 614, the trip plan and/or the control message is communicated to thevehicle data communication system for the vehicle data communicationsystem to implement the trip plan and/or the control message to controlmovement of the vehicle during the trip. The trip plan and/or thecontrol message is communicated according to the communicationconfiguration of the vehicle data communication system. After 614, flowof the method 600 may return to 610 to receive additional dataparameters regarding the vehicle, the route, or the trip itself. Theadditional data parameters may be used to generate a revised trip planand/or additional control messages that are communicated to thecommunication system. This sub-loop may continue until the communicativecoupling with the vehicle data communication system is severed, and uponsuch occurrence the method 600 returns to 602.

In an embodiment, a system includes an energy management system that hasone or more processors. The energy management system is configured to becommunicatively coupled with a communication system of a vehicle thattravels on a trip along a route. The energy management system isconfigured to receive data parameters related to at least one of thevehicle, the route, or the trip from the communication system. Theenergy management system is further configured to generate at least oneof a trip plan or a control message for the vehicle based on thereceived data parameters. The at least one of the trip plan or thecontrol message dictates tractive and braking efforts of the vehicleduring the trip. The energy management system is configured tocommunicate the at least one of the trip plan or the control message tothe communication system for the communication system to implement theat least one of the trip plan or the control message to control movementof the vehicle during the trip. The energy management system isconfigured to be removably coupled with the interface gateway devicesuch that the energy management system is mechanically disengageablefrom the interface gateway device.

In an aspect, the energy management system is a plug-in device thatincludes a housing that holds the one or more processors therein.

In another aspect, the energy management system includes an electricalconnector extending from the housing. The electrical connector isconfigured to removably mate to an electrical port of the communicationsystem to electrically connect the energy management system to thecommunication system.

In another aspect, the energy management system is configured tocommunicatively couple directly to an interface gateway device of thecommunication system.

In another aspect, the energy management system generates the at leastone of the trip plan or the control message to control movement of thevehicle during the trip in order to at least one of reduce fuelconsumption, reduce travel time, reduce wear on the vehicle, reach adestination at a predefined time, increase throughput on a vehiclenetwork, reduce emissions, or reduce noise.

In another aspect, the energy management system further includes amemory. The memory stores multiple communication configurations thereinthat specify at least one of rules or procedures for communicatingmessages with the communication system. The energy management system isconfigured to retrieve at least one of the communication configurationsstored in the memory to use the at least one communication configurationfor communicating with the communication system.

In another aspect, the energy management system further includes amemory. The memory stores multiple capability configurations thereinthat specify at least one of available control settings or formats ofthe communication system. The energy management system is configured toretrieve at least one of the capability configurations stored in thememory to use the at least one capability configuration for generatingcontent of the control message that is able to be implemented by thecommunication system.

In another embodiment, a system includes an interface gateway device andan energy management system. The interface gateway device is on acommunication system of a vehicle that travels on a trip along a route.The interface gateway device is configured to be communicatively coupledto a data acquisition module. The energy management system includes oneor more processors. The energy management system is configured to becommunicatively coupled to the interface gateway device. The energymanagement system is configured to be removably coupled with thecommunication system such that the energy management system ismechanically disengageable from the communication system. The interfacegateway device is configured to receive data parameters related to atleast one of the vehicle, the route, or the trip from the dataacquisition module and to communicate the data parameters to the energymanagement system. The energy management system is configured togenerate at least one of a trip plan or a control message for thevehicle based on the received data parameters and to communicate the atleast one of the trip plan or the control message to the interfacegateway device for the communication system to implement to control thevehicle during the trip.

In an aspect, the interface gateway device is configured to becommunicatively coupled to a controller that controls at least one of apropulsion subsystem or a braking subsystem of the vehicle. Theinterface gateway device is further configured to communicate the atleast one of the trip plan or the control message received from theenergy management system to the controller for the controller to controlthe at least one of the propulsion subsystem or the braking subsystemaccording to the at least one of the trip plan or the control message.

In another aspect, the data acquisition module is configured to acquirethe data parameters received by the interface gateway device from atleast one of a propulsion subsystem of the vehicle, a braking subsystemof the vehicle, a GPS receiver, a user interface device, a speedometer,a scheduler device, or an accelerometer.

In another aspect, the energy management system is a plug-in device thatincludes a housing that holds the one or more processors therein. Theenergy management system is configured to removably electrically connectwith the interface gateway device via an electrical connector.

In another aspect, the energy management system is configured toidentify the gateway interface device and to implement a communicationconfiguration associated with the gateway interface device whencommunicating the at least one of the trip plan or the control messageto the interface gateway device. The communication configurationspecifies at least one of rules or procedures for communicating messageswith the interface gateway device.

In another aspect, the energy management system is configured to receivethe data parameters and to generate the trip plan prior to the vehiclestarting on the trip. The trip plan dictates tractive and brakingefforts of the vehicle during the trip.

In another aspect, the energy management system is configured to receivethe data parameters and to generate the control message during the tripof the vehicle. The energy management system generates the controlmessage by comparing the received data parameters to the trip plan. Thetrip plan is generated prior to the vehicle starting on the trip. Thecontrol message dictates tractive and braking efforts of the vehiclebased on at least one of time or location of the vehicle along the routesuch that the vehicle travels according to the trip plan.

In another aspect, the interface gateway device is further configured tobe communicatively coupled to a user interface device that receives thecontrol messages from the energy management system during the trip ofthe vehicle. The energy management system is configured to identify theuser interface device and to implement a capability configurationassociated with the user interface device when generating content of thecontrol message. The capability configuration indicates availablecontrol settings and formats for presenting the content of the controlmessage to an operator.

In another embodiment, a method for controlling a vehicle during a tripalong a route includes determining whether a communicative coupling to acommunication system on the vehicle is established. If the communicativecoupling to the communication system is established, the method includesidentifying the communication system. The method also includesretrieving a communication configuration associated with thecommunication system that is identified. The method further includesreceiving data parameters from the communication system. The dataparameters are communicated according to the communicationconfiguration. The method includes generating at least one of a tripplan or a control message that dictates at least one of tractive effortsor braking efforts of the vehicle during the trip. The at least one ofthe trip plan or the control message is generated based on the receiveddata parameters and the capability configuration. The method alsoincludes communicating the at least one of the trip plan or the controlmessage to the communication system for the communication system toimplement the at least one of the trip plan or the control message tocontrol movement of the vehicle during the trip. The at least one of thetrip plan or the control message is communicated according to thecommunication configuration.

In an aspect, the method further includes retrieving a capabilityconfiguration associated with the communication system that isidentified. The capability configuration indicates available controlsettings and formats for the communication system or devices thereof.The at least one of the trip plan or the control message is generatedbased on the capability configuration in addition to the received dataparameters.

In another aspect, the generating step includes generating both the tripplan and the control message. The data parameters are received bothbefore the vehicle starts traveling on the trip and during the vehicletraveling on the trip. The trip plan is generated based on dataparameters received prior to the vehicle starting the trip. The controlmessage is generated during the vehicle traveling on the trip. Thecontrol message is generated by comparing the data parameters receivedduring the trip to the trip plan generated prior to the trip.

In another aspect, the communication system includes one or morecontrollers that control operations of a propulsion subsystem and abraking subsystem of the vehicle. The at least one of the trip plan orthe control message dictates tractive settings for the propulsionsubsystem and braking settings for the braking subsystem during thetrip. The communication configuration specifies at least one of rules orprocedures for communicating with the one or more controllers such thatthe one or more controllers implement the tractive settings and brakingsettings in response to receiving the at least one of the trip plan orthe control message.

In another aspect, the method further includes plugging an electricalconnector of an energy management system into a mating electricalconnector of an interface gateway device of the communication system tocommunicatively couple the energy management system to the communicationsystem such that the energy management system is mechanicallydisengageable from the communication system. The energy managementsystem is configured to generate the at least one of the trip plan orthe control message, i.e., in operation the energy management systemperforms the step(s) of generating the trip plan and/or the controlmessage.

In another embodiment, a data communication system for a vehicleincludes an interface gateway device that is configured to becommunicatively coupled with a data acquisition module and a clientmodule. The interface gateway device is further configured to receive avalue of a data parameter related to operation of the vehicle from thedata acquisition module and to communicate the value to the clientmodule for performing a function for the vehicle. The interface gatewaydevice also is configured to determine when either of the dataacquisition module or the client module is communicatively coupled withthe interface gateway device and to implement respective communicationconfigurations associated with the data acquisition module or the clientmodule to receive the value of the data parameter from the dataacquisition module or communicate the value of the data parameter to theclient module.

In another aspect, the interface gateway device is configured tocommunicate the value of the data parameter to the client module for theclient module to use the value of the data parameter to control at leastone of tractive effort or braking effort provided by the vehicle.

In another aspect, the interface gateway device is configured todetermine when either of the data acquisition module or the clientmodule is physically mated with one or more input/output ports of theinterface gateway device.

In another aspect, the interface gateway device is configured todetermine when either of the data acquisition module or the clientmodule is communicatively coupled with the interface gateway device by awireless communication link.

In another aspect, the interface gateway device is configured todetermine an identity of either of the data acquisition module or theclient module that is communicatively coupled with the interface gatewaydevice.

In another aspect, the interface gateway device is configured to selectat least one of a plurality of communication configurations from acomputer readable storage medium for use in communicating with the dataacquisition module or the client module based on the identity.

In another aspect, the communication configurations specify differentcommunication protocols used to communicate with different dataacquisition modules or different client modules.

In another embodiment, a data communication system for a vehicle isprovided. The system includes an interface gateway device that isconfigured to be communicatively coupled with a data acquisition moduleand with a client module. The interface gateway device is furtherconfigured to receive a value of a data parameter related to operationof the vehicle from the data acquisition module and to communicate thevalue to the client module for performing a function for the vehicle.The interface gateway device also is configured, upon systeminitialization of the interface gateway device, to cycle through aplurality of communication protocols available to the interface gatewaydevice, at each of a plurality of communication links of the interfacegateway device, until the interface gateway device has determined thatthe data acquisition module and the client module are communicativelycoupled with the interface gateway device and has identified first andsecond communication protocols of the plurality of communicationprotocols that enable the interface gateway device to communicate withthe data acquisition module and the client module, respectively.

In another embodiment, a method for communicating data in a vehicle isprovided. The method includes monitoring one or more input/output portsfor a communication link with a device, determining an identity of thedevice that is communicatively coupled with the one or more input/outputports by the communication link, selecting a communication configurationassociated with the device based on the identity of the device, andusing the communication configuration to communicate with the device.

In another aspect, the device includes one or more of a data acquisitionmodule or a client module, and the method further comprises one or moreof the data acquisition module acquiring values of data parametersrelated to operations of the vehicle or the client module performing oneor more functions for the vehicle based on the values of the dataparameters.

In another aspect, the method further comprises the client modulecontrolling at least one of tractive effort or braking effort of thevehicle based on the values of the data parameters.

In another aspect, the monitoring step includes determining when thedevice is physically mated with the one or more input/output ports.

In another aspect, the monitoring step includes determining when thedevice is communicatively coupled with the one or more input/outputports by a wireless communication link.

In another aspect, the selecting step includes selecting thecommunication configuration from a plurality of communicationconfigurations stored on a computer readable storage medium based on theidentity of the device.

In another aspect, the communication configurations specify differentcommunication protocols used to communicate with different devices.

In another embodiment, a computer readable storage medium for a vehiclehaving a processor is provided. The computer readable storage mediumincludes one or more sets of instructions that direct the processor tomonitor one or more input/output ports for a communication link with adevice, determine an identity of the device that is communicativelycoupled with the one or more input/output ports by the communicationlink, select a communication configuration associated with the devicebased on the identity of the device, and communicate with the deviceaccording to the communication configuration.

In another aspect, the computer readable storage medium is a tangibleand non-transitory computer readable storage medium. For example, thecomputer readable storage medium may not be a transient electric orelectromagnetic signal.

In another aspect, the one or more sets of instructions direct theprocessor to at least one of receive values of data parameters relatedto operations of the vehicle from a data acquisition module orcommunicate one or more of the values to a client module so that theclient module performs one or more functions for the vehicle based onthe values of the data parameters.

In another aspect, the one or more sets of instructions direct theprocessor to communicate values of data parameters related to operationsof the vehicle to the client module so that the client module controlsat least one of tractive effort or braking effort of the vehicle basedon the values of the data parameters.

In another aspect, the one or more sets of instructions direct theprocessor to determine when the device is physically mated with the oneor more input/output ports.

In another aspect, the one or more sets of instructions direct theprocessor to determine when the device is communicatively coupled withthe processor by a wireless communication link.

In another aspect, the one or more sets of instructions direct theprocessor to select the communication configuration from a plurality ofcommunication configurations stored on the computer readable storagemedium based on the identity of the device.

In another aspect, the communication configurations specify differentcommunication protocols used to communicate with different devices.

In another embodiment, a data communication system for a vehicle isprovided. The system includes a data acquisition module, a clientmodule, and an interface gateway module. The data acquisition module isconfigured to obtain a value of a data parameter related to operation ofthe vehicle. The client module is configured to use the value of thedata parameter to perform a function for the vehicle. The interfacegateway device is configured to be communicatively coupled with at leastone of the data acquisition module or the client module by one or morecommunication links. The interface gateway device is further configuredto communicate the value from the data acquisition module to the clientmodule. The interface gateway device also is configured to determinewhen the at least one of the data acquisition module or the clientmodule is communicatively coupled with the interface gateway device andto implement a communication configuration associated with the at leastone of the data acquisition module or the client module to communicatethe value of the data parameter to the at least one of the dataacquisition module or the client module.

It is to be understood that the above description is intended to beillustrative, and not restrictive. For example, the above-describedembodiments (and/or aspects thereof) may be used in combination witheach other. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the subject matterdescribed herein without departing from its scope. While the dimensionsand types of materials described herein are intended to define theparameters of the disclosed subject matter, they are by no meanslimiting and are exemplary embodiments. Many other embodiments will beapparent to one of ordinary skill in the art upon reviewing the abovedescription. The scope of the inventive subject matter should,therefore, be determined with reference to the appended claims, alongwith the full scope of equivalents to which such claims are entitled. Inthe appended claims, the terms “including” and “in which” are used asthe plain-English equivalents of the respective terms “comprising” and“wherein.” Moreover, in the following claims, the terms “first,”“second,” and “third,” etc. are used merely as labels, and are notintended to impose numerical requirements on their objects. Further, thelimitations of the following claims are not written inmeans-plus-function format and are not intended to be interpreted basedon 35 U.S.C. §112, sixth paragraph, unless and until such claimlimitations expressly use the phrase “means for” followed by a statementof function void of further structure.

This written description uses examples to disclose several embodimentsof the inventive subject matter, including the best mode, and also toenable a person of ordinary skill in the art to practice the embodimentsof inventive subject matter, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe inventive subject matter is defined by the claims, and may includeother examples that occur to a person of ordinary skill in the art. Suchother examples are intended to be within the scope of the claims if theyhave structural elements that do not differ from the literal language ofthe claims, or if they include equivalent structural elements withinsubstantial differences from the literal languages of the claims.

The foregoing description of certain embodiments of the presentinventive subject matter will be better understood when read inconjunction with the appended drawings. To the extent that the figuresillustrate diagrams of the functional blocks of various embodiments, thefunctional blocks are not necessarily indicative of the division betweenhardware circuitry. Thus, for example, one or more of the functionalblocks (for example, processors or memories) may be implemented in asingle piece of hardware (for example, a general purpose signalprocessor, microcontroller, random access memory, hard disk, and thelike). Similarly, the programs may be stand alone programs, may beincorporated as subroutines in an operating system, may be functions inan installed software package, and the like. The various embodiments arenot limited to the arrangements and instrumentality shown in thedrawings.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralof said elements or steps, unless such exclusion is explicitly stated.Furthermore, references to “one embodiment” of the present inventivesubject matter are not intended to be interpreted as excluding theexistence of additional embodiments that also incorporate the recitedfeatures. Moreover, unless explicitly stated to the contrary,embodiments “comprising,” “including,” or “having” an element or aplurality of elements having a particular property may includeadditional such elements not having that property.

Since certain changes may be made in the above-described systems andmethods, without departing from the spirit and scope of the inventivesubject matter herein involved, it is intended that all of the subjectmatter of the above description or shown in the accompanying drawingsshall be interpreted merely as examples illustrating the inventiveconcept herein and shall not be construed as limiting the inventivesubject matter.

What is claimed is:
 1. A system comprising: an energy management systemincluding one or more processors, the energy management systemconfigured to be communicatively coupled with a communication system ofa vehicle that travels on a trip along a route, the energy managementsystem being configured to receive data parameters related to at leastone of the vehicle, the route, or the trip from the communicationsystem, the energy management system further configured to generate atleast one of a trip plan or a control message for the vehicle based onthe received data parameters, the at least one of the trip plan or thecontrol message dictating tractive and braking efforts of the vehicleduring the trip; wherein the energy management system is configured tocommunicate the at least one of the trip plan or the control message tothe communication system for the communication system to implement theat least one of the trip plan or the control message to control movementof the vehicle during the trip, and wherein the energy management systemis configured to be removably coupled with the communication system suchthat the energy management system is mechanically disengageable from thecommunication system.
 2. The system of claim 1, wherein the energymanagement system is a plug-in device that includes a housing that holdsthe one or more processors therein.
 3. The system of claim 2, whereinthe energy management system includes an electrical connector extendingfrom the housing, the electrical connector being configured to removablymate to an electrical port of the communication system to electricallyconnect the energy management system to the communication system.
 4. Thesystem of claim 1, wherein the energy management system is configured tocommunicatively couple directly to an interface gateway device of thecommunication system.
 5. The system of claim 1, wherein the energymanagement system is configured to generate the at least one of the tripplan or the control message to control movement of the vehicle duringthe trip in order to at least one of reduce fuel consumption, reducetravel time, reduce wear on the vehicle, reach a destination at apredefined time, increase throughput on a vehicle network, reduceemissions, or reduce noise.
 6. The system of claim 1, wherein the energymanagement system further includes a memory, the memory storing multiplecommunication configurations therein that specify at least one of rulesor procedures for communicating messages with the communication system,wherein the energy management system is configured to retrieve at leastone of the communication configurations stored in the memory to use theat least one of the communication configurations for communicating withthe communication system.
 7. The system of claim 1, wherein the energymanagement system further includes a memory, the memory storing multiplecapability configurations therein that specify at least one of availablecontrol settings or formats of the communication system, wherein theenergy management system is configured to retrieve at least one of thecapability configurations stored in the memory to use the at least oneof the capability configurations for generating content of the controlmessage that is able to be implemented by the communication system.
 8. Asystem comprising: an interface gateway device on a communication systemof a vehicle that is configured to travel on a trip along a route, theinterface gateway device configured to be communicatively coupled to adata acquisition module; and an energy management system that includesone or more processors, the energy management system configured to becommunicatively coupled to the interface gateway device, the energymanagement system being configured to be removably coupled with theinterface gateway device such that the energy management system ismechanically disengageable from the interface gateway device; whereinthe interface gateway device is configured to receive data parametersrelated to at least one of the vehicle, the route, or the trip from thedata acquisition module and to communicate the data parameters to theenergy management system; wherein the energy management system isconfigured to generate at least one of a trip plan or a control messagefor the vehicle based on the received data parameters and to communicatethe at least one of the trip plan or the control message to theinterface gateway device for the communication system to implement tocontrol the vehicle during the trip.
 9. The system of claim 8, whereinthe interface gateway device is further configured to be communicativelycoupled to a controller that controls at least one of a propulsionsubsystem or a braking subsystem of the vehicle, the interface gatewaydevice being configured to communicate the at least one of the trip planor the control message received from the energy management system to thecontroller for the controller to control the at least one of thepropulsion subsystem or the braking subsystem according to the at leastone of the trip plan or the control message.
 10. The system of claim 8,wherein the data acquisition module is configured to acquire the dataparameters received by the interface gateway device from at least one ofa propulsion subsystem of the vehicle, a braking subsystem of thevehicle, a GPS receiver, a user interface device, a speedometer, ascheduler device, or an accelerometer.
 11. The system of claim 8,wherein the energy management system is a plug-in device that includes ahousing that holds the one or more processors therein, and the energymanagement system is configured to removably electrically connect withthe interface gateway device via an electrical connector.
 12. The systemof claim 8, wherein the energy management system is configured toidentify the gateway interface device and to implement a communicationconfiguration associated with the gateway interface device whencommunicating the at least one of the trip plan or the control messageto the interface gateway device, the communication configurationspecifying at least one of rules or procedures for communicatingmessages with the interface gateway device.
 13. The system of claim 8,wherein the energy management system is configured to receive the dataparameters and to generate the trip plan prior to the vehicle startingon the trip, the trip plan dictating tractive and braking efforts of thevehicle during the trip.
 14. The system of claim 8, wherein the energymanagement system is configured to receive the data parameters and togenerate the control message during the trip of the vehicle, the energymanagement system generating the control message by comparing thereceived data parameters to the trip plan, the trip plan being generatedprior to the vehicle starting on the trip, the control message dictatingtractive and braking efforts of the vehicle based on at least one oftime or location of the vehicle along the route such that the vehicletravels according to the trip plan.
 15. The system of claim 8, whereinthe interface gateway device is further configured to be communicativelycoupled to a user interface device that receives the control messagesfrom the energy management system during the trip of the vehicle, theenergy management system being configured to identify the user interfacedevice and to implement a capability configuration associated with theuser interface device when generating content of the control message,the capability configuration indicating available control settings andformats for presenting the content of the control message to anoperator.
 16. A method for controlling a vehicle during a trip along aroute comprising: determining whether a communicative coupling to acommunication system on the vehicle is established; if the communicativecoupling to the communication system is established, identifying thecommunication system; retrieving a communication configurationassociated with the communication system that is identified; receivingdata parameters from the communication system, the data parameterscommunicated according to the communication configuration; generating atleast one of a trip plan or a control message that dictates at least oneof tractive efforts or braking efforts of the vehicle during the trip,the at least one of the trip plan or the control message generated basedon the received data parameters; and communicating the at least one ofthe trip plan or the control message to the communication system for thecommunication system to implement the at least one of the trip plan orthe control message to control movement of the vehicle during the trip,the at least one of the trip plan or the control message communicatedaccording to the communication configuration.
 17. The method of claim16, further comprising retrieving a capability configuration associatedwith the communication system that is identified, the capabilityconfiguration indicating available control settings and formats for thecommunication system or devices thereof, the at least one of the tripplan or the control message being generated based on the capabilityconfiguration in addition to the received data parameters.
 18. Themethod of claim 16, wherein the generating step includes generating boththe trip plan and the control message, the data parameters beingreceived both before the vehicle starts traveling on the trip and duringthe vehicle traveling on the trip, the trip plan generated based on dataparameters received prior to the vehicle starting the trip, the controlmessage generated during the vehicle traveling on the trip, the controlmessage generated by comparing the data parameters received during thetrip to the trip plan generated prior to the trip.
 19. The method ofclaim 16, wherein the communication system includes one or morecontrollers that control operations of a propulsion subsystem and abraking subsystem of the vehicle, the at least one of the trip plan orthe control message dictating tractive settings for the propulsionsubsystem and braking settings for the braking subsystem during thetrip, the communication configuration specifying at least one of rulesor procedures for communicating with the one or more controllers suchthat the one or more controllers implement the tractive settings andbraking settings in response to receiving the at least one of the tripplan or the control message.
 20. The method of claim 16, furthercomprising plugging an electrical connector of an energy managementsystem that is a removable plug-in device into a mating electricalconnector of an interface gateway device of the communication system tocommunicatively couple the energy management system to the communicationsystem such that the energy management system is mechanicallydisengageable from the communication system, wherein the energymanagement system generates the at least one of the trip plan or thecontrol message.